feat(desktop): add LAN mobile remote control - #41392
Draft
AlexZander85 wants to merge 35 commits into
Draft
Conversation
Contributor
|
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
github-actions
Bot
added
needs:title
needs:compliance
AlexZander85
changed the title
AlexZander85
marked this pull request as draft
August 9, 2026 10:35
github-actions
Bot
removed
needs:title
needs:compliance
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Related to #10288
Type of change
What does this PR do?
Adds LAN-only remote control for an existing OpenCode Desktop session.
From the session header, the user can open Remote Control, scan a QR code with a phone on the same local network, and control that session through a session-scoped mobile interface.
The remote interface supports:
The implementation intentionally does not expose the full sidecar API, terminal access, filesystem access, or Internet/relay access.
Pairing uses a short-lived one-time ticket which is exchanged for a revocable session-scoped grant. The Desktop LAN gateway only proxies
/remote/*.This is a draft PR mainly to get feedback on whether this narrower LAN-only approach fits the project direction.
How did you verify your code works?
Added targeted unit/integration coverage for pairing, session-scoped authorization, cross-session rejection, bootstrap/event filtering, text-only prompts, revoke/session deletion, pairing lifecycle races, LAN address changes, and gateway boundaries.
Also ran a browser-level Chromium/Playwright smoke test of the production mobile UI covering pairing, permission reply, question reply, sending a prompt, live refresh, and stop/abort.
The browser flow completed without page errors. Physical phone-to-Desktop LAN testing and upstream CI are still pending.
Screenshots / recordings
Checklist